Risk Signal: Colombian Registraduria Check
Jumio has a database check service available for the Colombian Registraduria database. This check verifies that a provided Colombian ID number and related user information corresponds to existing government records.
Supported Credentials
The following values can be uploaded as Prepared Data. Alternatively, they can be extracted by an upstream capability in a workflow.
To use with the standard Jumio IDIV service use workflow key 10054.
To use Prepared Data with the Colombian Registradurias Check as a standalone capability use workflow key 10020.
Key |
Type |
Mandatory |
Description |
---|---|---|---|
firstName |
string |
yes |
|
lastName |
string |
yes |
|
middleName |
string |
no |
|
paternalSurname |
string |
no |
|
maternalSurname |
string |
no |
|
dateOfBirth |
LocalDate |
yes |
Date of birth in yyyy-MM-dd format only |
id |
Object |
yes |
See in next row |
id.idNumber |
string |
yes |
NUIP number. Do not include periods. Example: "1234567890" |
id.type |
string |
yes |
|
id.issuingDate |
string |
no |
Date the ID was issued in yyyy-MM-dd format only |
address |
object |
yes |
|
address.country |
string |
yes |
COL Country in ISO-3166-1 Alpha-3 Code or ISO-3166-1 Alpha-2 Code format.
|
Example Prepared Data Body
{ "firstName": "XXXXXX", "lastName": "XXXXXX", "dateOfBirth": "1959-04-22", "paternalSurname": "XXXXXX", "maternalSurname": "XXXXXX", "address": { "country": "COL" ) }, "id": { "idNumber": "XXXXXXXXXX", "type": "ID_CARD", "issuingDate": "1977-09-01" } }
Response
Response data is available for transactions that include the risk signal. For information on transaction data see Viewing or Retrieving Workflow Transactions.
Example Response
"govtIdVerification": [ { "id": "721a8178-162e-4ff4-8ab3-4194ceb0e310", "credentials": [ { "id": "6248205a-3194-4a23-b5be-515306729583", "category": "DATA", "label": "DATA" } ], "decision": { "type": "PASSED", "details": { "label": "OK" } }, "data": { "completeNameMatch": "MATCH", "firstNameMatch": "MATCH", "lastNameMatch": "MATCH", "nationalIdMatch": "MATCH", "dobMatch": "MATCH", "issuingDateMatch": "MATCH", "paternalSurnameMatch": "MATCH", "maternalSurnameMatch": "MATCH", "statusCode": "0", "statusDescription": "Valid/Active" } } ]
Decision Details Labels
Decision Type |
Label |
Description |
---|---|---|
NOT_EXECUTED |
PRECONDITION_NOT_FULFILLED |
Provided data is incomplete or incorrectly formatted. |
NOT_EXECUTED |
TECHNICAL_ERROR |
The service encountered an error and was unable to process the request. |
NOT_EXECUTED |
PERMISSION_DENIED |
The request is not authorized to access the service. |
PASSED |
OK |
|
WARNING |
ALERT |
The NUIP number is valid but other data may not match. |
REJECTED |
DENY |
The NUIP number is invalid or does not match the provided data. |
Data
Key |
Type |
Description |
---|---|---|
firstNameMatch* | string |
|
lastNameMatch* | string |
|
completeNameMatch* |
string |
|
nationalIdMatch | string |
|
dobMatch | string |
|
issuingDateMatch |
string |
|
paternalSurnameMatch* |
string |
|
maternalSurnameMatch* |
string |
|
statusCode |
string |
Status code number. |
statusDescription |
string |
Description of the status associated with the status code. |
* The firstNameMatch, lastNameMatch, paternalSurnameMatch, and maternalSurnameMatch fields will be returned only if the granular name values are provided as Prepared Data. If the name is extracted from an ID document, only the completeNameMatch field will be returned, as shown in the following example:
"govtIdVerification": [ { "id": "7502be48-390c-4796-989e-5000e59c7e8e", "credentials": [ { "id": "38317d8c-7b5f-4b8f-b21a-f3757b1b86c1", "category": "ID" } ], "decision": { "type": "PASSED", "details": { "label": "OK" } }, "data": { "country": "COL", "type": "ID_CARD", "completeNameMatch": "MATCH", "nationalIdMatch": "MATCH", "dobMatch": "MATCH", "issuingDateMatch": "MATCH","statusCode": "0", "statusDescription": "Valid/Active" },